-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecureComms: Add support for inbound network namespace #2048
SecureComms: Add support for inbound network namespace #2048
Conversation
b6662c0
to
0bb9a73
Compare
a09eb6b
to
3caa67e
Compare
85a4725
to
3ce165c
Compare
a2eb53b
to
839c9d7
Compare
839c9d7
to
d980cb3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you very much!
d980cb3
to
12d5a83
Compare
cc: @bpradipt |
12d5a83
to
5d55342
Compare
0761631
to
e759430
Compare
716d98c
to
786081c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thanks @davidhadas
Support opening inbound ports in configrable network namespaces. This allows opening an inbound port inside the pod network namespace of the podvm. The traffic will be forwarded via the SecureComms ssh channel to the outbound at the worker node. Signed-off-by: David Hadas <[email protected]>
786081c
to
44baf22
Compare
See:
Support opening inbound ports in configurable network namespaces.
This allows opening an inbound port inside the pod network namespace of the podvm.
The traffic will be forwarded via the SecureComms ssh channel to the outbound at the worker node.